Summary

Adds BBOPlace as two Frontier-CS 2.0 Harbor tasks using the unified 2.0 adapter:

• bboplace_ispd2005
• bboplace_iccad2015

The tasks use CPU-only MP-HPWL evaluation against relaxed MGO baselines from BBOPlace-Bench. Public iterative feedback evaluates the first benchmark in each suite, while final verification reruns the final submission and best iterative artifact across the full benchmark suite.

This also updates the unified 2.0 Harbor adapter to support a separate judge Docker image, so BBOPlace benchmark data/runtime can live in the judge container without changing the agent container or affecting other 2.0 tasks.

Please read CONTRIBUTING.md before submitting.

Type of Change

• New research problem
• New algorithmic problem
• New Frontier-CS 2.0 problem
• Bug fix
• Documentation update
• Other:

Testing

• python3 tools/bboplace/check_constants.py
• PYTHONPYCACHEPREFIX=/private/tmp/frontier-cs-pycache python3 -m py_compile 2.0/problems/bboplace_ispd2005/evaluator.py 2.0/problems/bboplace_iccad2015/evaluator.py adapters/frontier-cs-2.0/src/frontier_cs_2_0/adapter.py adapters/frontier-cs-2.0/src/frontier_cs_2_0/utils.py
• Generated BBOPlace Harbor tasks with the unified 2.0 adapter:
  • bboplace_ispd2005
  • bboplace_iccad2015
• python3 tools/bboplace/check_generated_tasks.py /private/tmp/frontier-cs-bboplace-generated
• Generated upstream non-BBOPlace task vector_db_ann_relaxed as an adapter smoke test.
• Confirmed the generated vector_db_ann_relaxed task does not reference the BBOPlace judge image or BBOPlace data.
• Ran Harbor trials that reached positive quick scores:
  • bboplace_ispd2005: positive quick score on adaptec1
  • bboplace_iccad2015: positive quick score on superblue1

Checklist

• Code follows the project structure and conventions
• Self-review completed
• Documentation updated (if applicable)

CI Validation (for new problems)

When adding new problems, CI will automatically validate that your reference solution achieves score > 0.

• Algorithmic problems: Include reference.cpp in your problem directory
• Research problems: Include reference.py (or reference.cpp if language: cpp in config.yaml)
• 2.0 problems: Include reference.py unless the problem config declares another language

Both new 2.0 problems include reference.py.